home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware Overload Trio 2
/
Shareware Overload Trio Volume 2 (Chestnut CD-ROM).ISO
/
dir38
/
blnks415.zip
/
BLANKS.MSG
< prev
next >
Wrap
Text File
|
1993-12-01
|
12KB
|
305 lines
╒══════════════════════════════════════════╕
│ BLANKs │
│ Revision 4.15.0 │
│ │
│ Copyright (C) 1988-1993 FM de Monasterio │
│ Licensed Material. All Rights Reserved │
╘══════════════════════════════════════════╛
║ ║╔═╗╔═╣╔═╗╠═ ╔═╗
║ ║║ ║║ ║╔═╣║ ╠═╝
╚═╝╠═╝╚═╝╚═╝╚═╝╚═╝
MESSAGES
********
Program execution is halted immediatedly after messages with "Abort"
headers and some messages with "Error" headers. Execution continues
after messages with a "Warning" header, some messages with an "Error"
header, and most other messages.
The following is a brief explanation of program messages:
1. "Abort: Program code corrupted (CRC error)"
-------------------------------------------
Upon its execution, the program failed its internal verification
check, indicating corruption of the code.
2. "Abort: Program requires 286 compatible CPU"
"Abort: Program requires 386 compatible CPU"
"Abort: Program requires 486 compatible CPU"
------------------------------------------
286 program releases cannot be executed in 086/88 or most 186/188
machines; 386 program releases cannot be executed in 086/88, 186/
188, and 286 machines; 486 program releases cannot be executed in
086/88, 186/188, 286, and 386 machines.
3. "Abort: Needs MS-compatible DOS 3 or later"
----------------------------------------------
The program requires a DOS version equal to or greater than MS-DOS 3
or compatible DOS system version.
4. "Abort: Unknown video/incompatible controller"
----------------------------------------------
The program was unable to determine the type of video adapter in use.
Adapters currently recognized are SVGA, VGA, MCGA, EGA, CGA, MDA, and
the HERCULES HGC, HGC+, and InColor cards. Alternatively, testing of
the video circuitry revealed hardware incompatibilities.
5. "Installed at absolute address ????0h"
"Enter <BLANKS /?> for Help"
--------------------------------------
BLANKs was successfully executed and the resident(s) installed at the
indicated (hexadecimal) memory address.
6. "Using default blanking parameters"
-----------------------------------
No parameters were specified, and BLANKs is using its default values.
7. "Resident updated"
"Enter <BLANKS /?> for Status"
------------------------------
The relevant resident parameters of BLANKs were successfuly updated.
8. "Resident quiescent"
--------------------
Switch QU was specified, and the program now remains inactive until
the next program execution, if switches /? or QU were not specified
at that time.
9. "Error: DOS environment unchanged [code ?]"
-------------------------------------------
The program was unable to create/update the requested DOS environment
string. The following codes may be expected:
0: An unrecognized DOS version is being used.
1: Not enough room in the global environment block.
2: Null terminator for environment block not found.
3: Null size environment block.
Error 1 may be due to a small DOS environment block. Errors 2 and 3
indicate corruption of the environment block.
10. "Resident already loaded: Switch /WA ignored"
---------------------------------------------
WINDOWS 3.x awareness (386-Enhanced & Standard mode) can be specified
only before the resident installation. Unload resident and reload it
after specifying switch WA, if this awareness is needed.
11. "Resident already loaded: Switch /RK ignored"
---------------------------------------------
Keyboard access monitoring must be specified (via /RK, /RK+, or /RK-)
before the resident installation, and such monitoring can be modified
afterwards. This message indicates that the keyboard monitoring code
was not loaded; unload resident and reload it after specifying switch
RK+ or RK-, if keyboard access monitoring is needed.
12. "Mouse driver not loaded or inactive"
-------------------------------------
The program did not find a mouse driver compatible with the Microsoft
or Logitech Mouse format. Thus, mouse blanking and unblanking cannot
be implemented.
13. "Error: Invalid mouse button for blanking"
14. "Error: Invalid screen corner for blanking"
-------------------------------------------
An invalid selection for mouse blanking was made by the user. Mouse-
blanking status is not modified.
15. "Not enough RAM to preserve screen contents"
"Only ???? bytes are available..."
"Continue? [Yn] "
--------------------------------------------
When switch /?, PW?, or HK? is selected, BLANKs attempts to allocate
an additional 8,288 bytes for video data processing. The message is
displayed if enough RAM is not available (other program services can
still be executed). Press <Y> or <Enter> to proceed with the display
or <N> or <Esc> to cancel the execution. *NOTE: If the mouse driver
is active, and <Y> is pressed, the mouse status will not be restored
at the exit from BLANks.
16. "User BREAK"
------------
The Ctrl-Break key was pressed during an interactive screen display.
17. "Unable to restore Mouse state - Driver reset"
----------------------------------------------
The buffer preserving the Mouse state data was found to be corrupted
after an interactive display. The mouse driver has been reset.
18. "Error: Invalid switch Xx in command /Xx"
-----------------------------------------
An invalid switch designator (X) or parameter (x) was encountered.
Switch parsing continues after the next switch delimiter.
19. "Error: Not a VGA system"
-------------------------
Switch BC was selected for a nonVGA adapter system.
20. "Current and initial video address differ"
------------------------------------------
The current video system differs from that detected by the BIOS at
machine boot up time. The current system is considered the primary
one for the purposes of the program.
21. "Password string: xxxxxx"
-------------------------
If the password is specified directly from the DOS command line, the
specification is echoed at the end of the program execution, so that
the password can be rechecked. The echoimg can be redirected through
the DOS prompt redirection command '>'.
22. "Invalid character in password string <?>"
"Use alphanumeric (A-Z or 0-9) characters"
------------------------------------------
An invalid character was entered during the password selection. A
sequence of 1 to 15 non-shifted, alphanumeric-only characters (A-Z
0-9) is required.
23. "Abort: Password verification failure"
--------------------------------------
Execution is cancelled after 5 attempts to verify the password.
24. "Error: /HKxn parameter {x} must be A-Z or 0-9"
-----------------------------------------------
An invalid character was entered as the first parameter of the new
hotkey. Use any character between <A> to <Z> or <0> to <9>.
25. "Error: /HKxn parameter {n} must be 4 ≥ n ≥ 15"
-----------------------------------------------
An invalid character was entered as the second parameter of the new
hotkey. Use a number between 4 and 15 to specify the corresponding
<Right shift>, <Left shift>, <Alt>, and <Ctrl> combination.
26. "Resident uninstalled"
----------------------
The BLANKs resident was successfuly deallocated from memory.
27. "Resident not yet installed"
----------------------------
Resident uninstalling was requested but the program has not yet been
installed.
28. "Cannot uninstall: Interrupt(s) ??h in use"
-------------------------------------------
The indicated interrupt vectors are still in use by another resident
loaded after BLANKs was installed. All of the changed interrupt are
listed. The uninstall request is not honored as this would hang the
machine.
29. " Error: Block not released [DOS code ??h] at address ????0h"
--------------------------------------------------------------
DOS did not deallocate the memory block allocated to the resident at
the time of installation. One of two error codes may be expected:
7 - Memory blocks above the DOS area trashed.
9 - Invalid block request.
These errors indicate a corruption of the memory control chain of the
operating system. Reboot system as soon as possible.
30. " Error: Block not released [XMS code ??h] at address ????0h"
--------------------------------------------------------------
The XMM did not deallocate the UMB allocated to the resident at the
time of installation. One of two error codes may be expected:
8Eh - General driver error occurred.
8Fh - Unrecoverable driver error occurred.
These errors indicate a corruption of the XMS manager. Reboot system
as soon as possible.
31. "Error: Compatible XMS manager not detected"
--------------------------------------------
BLANKs failed to determine presence of a driver compatible with the
Extended Memory Specification (XMS) version 2.0+, and the requested
UMB load (/LH) defaulted to conventional memory installation.
32. "Error: Unable to allocate UMB [XMS code ??h]"
----------------------------------------------
The XMM did not allocate the requested UMB. One of the following
XMS error codes may be expected:
80h - Function is not implemented.
8Eh - General driver error occurred.
8Fh - Unrecoverable driver error occurred.
B0h - Smaller UMB is available.
B1h - No UMBs are available.
B2h - UMB segment number is invalid.
33. "Error: Unable to allocate UMB [DOS code ??h]"
----------------------------------------------
MS-DOS 5+ did not allocate the requested UMB. One of the following
error codes may be expected:
7 - Memory blocks above the DOS area trashed.
8 - Not enough memory.
Error 7 indicates a corruption of the memory control chain of the
operating system (reboot processor as soon as possible). Error 8
indicates that no UMBs are available. Install the program in low
memory.
34. "NON-RECOVERABLE DOS MEMORY ERROR! [code ??h]"
"Reboot machine as soon as possible..."
----------------------------------------------
MS-DOS 5+ did not restore its default memory allocation strategy
after the program modified it for UMB allocation; the error code
may be 01h (invalid function). Reboot the machine immediately.
35. "Error: UMA linkage not restored [DOS code ??h]"
------------------------------------------------
MS-DOS 5+ did not restore the original link status with the upper
memory area. Although not critical, this error should not occur,
amd it may be better to reboot the mchine.
36. "Unable to allocate UMB above minimum address"
----------------------------------------------
A free upper-memory block was not available above the lower high-
memory address specified by switch LHn. Resident was installed at
a lower UMB whose value is displayed in the installation message.
┌─────────────────────────────────────────────────────────────┐
│ Trademarked names are the property of the respective owners │
└─────────────────────────────────────────────────────────────┘
[End]